Shareware Grab Bag

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Grab Bag / Shareware Grab Bag.iso / 086 / ros38doc.arc / ROSSYS.DOC < prev next >

Wrap

Text File | 1988-01-10 | 120.4 KB | 3,304 lines

RRRRRR OOOOO SSSSS RR RR OOO OOO SS SS RR RR OO OO SS RR RR OO OO SS RRRRRR OO OO SSSSS RRRR OO OO SS RR RR OO OO SS RR RR OOO OOO SS SS RR RR OOOOO SSSSS Remote Operating System S Y S O P M A N U A L Copyright (c) 1985 - 1988 All Rights Reserved by Steven Fox 2112 White Cloud NE Albuquerque, New Mexico 87112 USA DISTRIBUTION RIGHTS Free, public access bulletin boards are welcome to use ROS with- out charge. If you and your users find ROS fast and easy to use, a contribution would be appreciated. Licensed systems will be registered to receive a diskette and printed documentation of the next version of ROS when available. Please state the current version that you have. Commercial and government sponsored sys- tems, including those which assess a fee for access, must be licensed (an invoice is provided at the end of this document). You may freely copy and distribute this software and documenta- tion only in its original, unmodified state. This allows distri- bution via bulletin boards, user groups, and distributors of public domain and shareware software. Other than reasonable copying, shipping, and handling charges, no remuneration may be accepted by any party other than the copyright holder. Licensed systems may print copies of the User Manual as required. Please refer all inquiries and comments about ROS to Sysop Albuquerque ROS (505)299-5974 300/1200/2400 bps, no parity, 8 bit characters, 1 stop bit or to Steven Fox 2112 White Cloud NE Albuquerque, NM 87112 DISCLAIMER ROS and its associated programs are provided AS IS, without warranty of any kind, expressed or implied, including, but not limited to, fitness for a particular purpose. In no event will the author be liable for any damages arising out of their use. T A B L E O F C O N T E N T S 1. HISTORY AND ACKNOWLEDGMENTS................................1 2. MINIMUM SYSTEM.............................................2 3. FILES......................................................3 4. INSTALLING ROS.............................................4 4.1. Configuring DOS.......................................4 4.2. Message and file area control file - AREA.ROS.........4 4.3. ROS configuration file - CONFIG.ROS...................7 4.4. System message file - SYSMTXT.ROS....................13 4.5. Other files used by ROS..............................16 5. USING THE SYSTEM..........................................18 5.1. Logging in the first time............................18 5.2. Status line..........................................18 5.3. When ROS is idling between users.....................19 5.4. Local console commands...............................19 5.4.1. C/R Using ROS locally........................19 5.4.2. F2 Direct connection........................19 5.4.3. F3 Delayed disable..........................20 5.4.4. F4 Disable remote I/O.......................20 5.4.5. F5 Sysop initiated CHAT.....................20 5.4.6. F6 Signal key...............................20 5.4.7. F7 Internal key.............................20 5.4.8. F8 Message key..............................20 5.4.9. F9 Twit key.................................21 5.4.10. Shutdown ROS.................................21 6. MAINTENANCE...............................................22 6.1. Sysop Sub-system.....................................22 6.2. <A>udit trail toggle.................................22 6.3. <C>atalog operations.................................23 6.3.1. uild.......................................23 6.3.2. <D>escribe....................................23 6.3.3. <E>dit........................................24 6.3.3.1. Add..................................24 6.3.3.2. Backward.............................24 6.3.3.3. Change...............................24 6.3.3.4. Delete...............................25 6.3.3.5. Edit.................................25 6.3.3.6. Forward..............................25 6.3.3.7. Hide.................................26 6.3.3.8. Next.................................26 6.3.3.9. Previous.............................26 6.3.3.10. Release.............................26 6.3.3.11. Select..............................26 6.3.3.12. Quit................................26 6.3.4. <G>lobal......................................26 6.3.5. <L>eaders.....................................27 6.3.6. ost........................................27 6.3.7. <R>econcile...................................27 6.3.8. <Q>uit........................................28 ii 6.4. <E>dit user record...................................28 6.4.1. <A>dd record..................................28 6.4.2. <D>elete record...............................28 6.4.3. <E>dit record.................................28 6.4.4. <F>orce password..............................28 6.4.5. <N>ext record.................................29 6.4.6. revious record.............................29 6.4.7. <R>egistered..................................29 6.4.8. <S>elect record...............................29 6.4.9. <V>alidate user...............................29 6.4.10. <Q>uit edit session..........................29 6.5. nitialize system files............................29 6.6. <J>ump to DOS........................................30 6.7. <L>ist system files..................................30 6.7.1. <A>ll system files............................30 6.7.2. <L>og file....................................30 6.7.3. <M>essages....................................30 6.7.4. <Q>uit........................................30 6.8. <O> Macro operations.................................30 6.8.1. Time Initiated Macro..........................31 6.8.2. Macro Examples................................31 6.9. urge files........................................32 6.9.1. Purge All.....................................32 6.9.2. Purge Catalog.................................32 6.9.3. Purge Log.....................................32 6.9.4. Purge Messages................................32 6.9.5. Purge Users...................................33 6.10. <T>oggle printer....................................33 6.11. <V>ersions..........................................33 6.12. Other commands available to the sysop...............33 6.12.1. <G>oodbye (logoff)..........................33 6.12.2. <F>ile Transfer System......................33 6.12.3. <M>essage System............................33 6.12.4. tility System............................33 6.12.5. <X>pert mode toggle.........................33 6.12.6. Command Enhancements........................34 6.12.6.1. Changing a Message Status or Mess.34 6.12.6.2. Setting the System Time and Date..34 6.12.6.3. User List Additions...............34 7. SECURITY..................................................36 8. COMMAND LINE OPTIONS......................................37 8.1. Option /r............................................37 8.2. Option /d............................................38 8.3. Option /m............................................38 8.4. Option /o=...........................................38 9. OTHER VERSIONS OF ROS.....................................39 ii Appendices A. CONNECTING THE MODEM......................................40 B. BUILDING A NEW FILE CATALOG...............................42 C. WARNING AND ERROR MESSAGES................................43 D. ROS USAGE AND PROBLEM REPORT..............................46 E. INVOICE...................................................48 INDEX.....................................................49 iii L I S T O F F I G U R E S 4-1: Hayes Modem Initialization Command String................12 6-1: Sysop Sub-System.........................................22 iv L I S T O F T A B L E S 3-1: Files Included with ROS...................................3 3-2: Files Required for Conversion ROS from Previous Version...3 4-1: AREA.ROS File (split between columns 62 and 63)...........5 4-2: Positional Fields in AREA.ROS File........................5 4-3: Required Entries in AREA.ROS..............................6 4-4: Configuration Parameters.................................11 4-5: Color Scale..............................................12 4-6: System Message Text File.................................16 4-7: Files Used by ROS........................................17 6-1: Format of User File Listing..............................35 C-1: Error Messages...........................................45 v ROS Sysop Manual 1. HISTORY AND ACKNOWLEDGMENTS The original SJBBS, written in Xitan Basic by Howard Moulton, was adapted to MBasic by Bruce R. Ratoff. Modifications to this system were made by Bruce Ratoff, James Underwood, Ron Fowler, Brett Berg, and many, many others. James Whorton and Eddie H. Curlin converted RBBS to Turbo Pascal (copyright Borland Interna- tional) in 1984 and called the system TPBBS. ROS version 1.0 (originally released as "TBBS23" but changed to "ROS" to avoid confusion with TPBBS with which it shares no code) was written by Steven Fox using ideas gathered from these systems and from others operating on a wide variety of computers. Version 2.0 used indexed file support using B+ trees. Version 3.0 incorporated all the communication and file transfer functions to eliminate the need for support from programs such as "XMODEM" and "BYE." Though originally tied to CP/M-80. Version 3.5 was built to operate under PC DOS. Version 3.6 provided improved archive support as well as several new functions for the sysop. Version 3.7 completed the archive support with the ability to type text files and adds an automatic file posting system coupled with a descriptive file catalog. Version 3.8 added the capability to output menus and bulletins which include ANSI control sequences for color and graphic characters. ROS would not have been possible were it not for the work of the many individuals dedicated to making the concept of public access telecommunications work. 1 ROS Sysop Manual 2. MINIMUM SYSTEM ROS version 3.8 is designed to operate on an IBM PC, or very compatible computer, with at least 256K of memory. Version 2.0 or later DOS is required. The only required support program is LCOMX (see Section 4.1), though file and text managers such as CWEEP, ARC and PC-WRITE are useful for some off-line maintenance functions. ROS has been tested under versions 3.1 through 3.3 of PC DOS and versions 3.1 and 3.2 of MS-DOS. ROS is aware of several multi- tasking systems (DESQview, TopView, MicroSoft Windows, DoubleDOS, and TaskView) and will relinquish any unneeded time to tasks running in other windows. When used with one of these environments, ROS requires 160 k-bytes of memory. If the ability to jump to DOS is desired, additional memory will be required. 2 ROS Sysop Manual 3. FILES Table 3-1 lists the files that are included with this version of ROS. Table 3-2 lists the files that are needed to update pre- vious versions of ROS. ROS.COM Main executable code for ROS ROS.000 Overlay files ROS.001 ROS.002 ROS.003 AREA.ROS Sample area file CONFIG.ROS Sample system configuration file MACRO.ROS Sample macro file SYSMTXT.ROS Sample message file RO-PIF.DVP DESQview program information file ROSUSR.DOC User Guide ROS.MAP ROS command map ROSSYS.DOC System Operations Manual (this document) ARCHIVE.BAT Batch file to archive the CATALOG REMOTE.BAT Batch file to redirect the console to COM 1 RETURN.BAT Batch file to return control to ROS Table 3-1: Files Included with ROS ROS37-38.COM ROS file conversion utility RELEASE.NOT Text file describing the changes to ROS Table 3-2: Files Required for Conversion ROS from Previous Version 3 ROS Sysop Manual 4. INSTALLING ROS ROS is already installed for the display on most IBM and compat- ible computers and does not require a graphics or color adapter, though it works well with CGA and EGA monitor cards. Three text files are used to match ROS to your message and file structure, modem, and personal preferences. The first of these three files, "AREA.ROS" describes the message and file structure, i.e. what message and file areas are avail- able and what access levels are required. "CONFIG.ROS" contains many parameters to match ROS to your computer system, including the modem and a color monitor, if available. The third file, "SYSMTXT.ROS" is the system message file. It contains the mes- sages, bulletins, and menus sent to the user during various stages of operation. Each file is described in more detail in the following sections. 4.1. Configuring DOS Two changes should be made to your system, the first to your CONFIG.SYS file and the second to your AUTOEXEC.BAT (please refer to your DOS manual for more information about these two files). CONFIG.SYS Include the statement "FILES = 20" in your CONFIG.SYS file. This will allow ROS to open all the files it needs to operate. If you already have a "FILES" statement with a value greater than 20, you don't need to change it. Please refer to your DOS manual for more information about the CONFIG.SYS file (not to be confused with the CONFIG.ROS file). Also, after making changes to CONFIG.SYS, DOS must be rebooted. AUTOEXEC.BAT LCOMX.EXE provides ROS with the interrupt driven interface to the communication port. LCOMX.EXE is a memory resident utility that need to be run only once after the computer is booted, regardless of how many times ROS is run. The simplest approach is to include "LCOMX" in your AUTOEXEC.BAT file. Remember, LCOMX must be run before ROS. 4.2. Message and file area control file - AREA.ROS The message and file area control file, AREA.ROS is used to control access to specific file and message areas. A sample of the area file is shown in table 4-1. Table 4-2 lists each field and the field positions. 4 ROS Sysop Manual The entries shown in the table 4-1 are expected by ROS and must be present in the area file. The message area for POST and the directory path to LOGIN and NEWIN may be changed to any value and the access levels for these entries may also be set to any value. Table 4-3 describes each of these entries in more detail. Column 1 2 3 4 5 6 12345678901234567890123456789012345678901234567890123456789012 MAIL Mail and messages addressed to you SENT Mail and messages you have sent WORLD Public messages from all areas SYSTEM System wide message access POST Trading Post - Buy, Sell, Trade LOGIN Login area NEWIN ** New uploads ** Column 7 3456789012345678 10 0 10 0 10 0 255 0 10 1 10 C:\ROS\LOGIN 20 C:\ROS\NEWIN Table 4-1: AREA.ROS File (split between columns 62 and 63) Area name 1-12 Area description 13-62 Access level required 63-65 Must be blank 66 DOS directory path, or 67-131 Message area number Table 4-2: Positional Fields in AREA.ROS File 5 ROS Sysop Manual MAIL When the user logs into this message area, ROS will build a list of the mail addressed to that user. The message area number should be "0" and the access level should be set low enough that unvalidated users have access. SENT This message area is used to access messages and mail the user has sent. The message area number and access level should be set as in "MAIL." WORLD This is not a single message area but a cross-section of the various message areas to which the user has access, not including "MAIL" and "SENT." The access level is ignored. Instead, ROS uses the access level for each individual message area to determine if the user has access to a message. The message area number should be "0." SYSTEM This message area is special since ALL mail and messages, regardless of the sender and addressee, (including those that have been deleted but not yet purged) will be included. THE ACCESS LEVEL OF THIS AREA SHOULD BE SET HIGH ENOUGH THAT NORMAL USERS DO NOT HAVE ACCESS. The access level defined for "AltSysop" (see CONFIG.ROS) is recommended. POST This is the message area that every user "sees" initially. The access level should be set low enough that new users have access on their first call ("0" is recommended). LOGIN This is the file area that every user "sees" initially. The access level should be set low enough that new users have access on their first call ("0" is recommended). NEWIN This is the file area into which uploads will be placed. The access level of this area may be any value. Table 4-3: Required Entries in AREA.ROS NOTE: AREA.ROS should NOT have extra lines after the last line of information. In addition, unlike the system message file de- scribed in section 4.4, ROS cannot process high-order bits in the text of this file, so an editor must be used which does not use these bits. WordStar, in non-document mode, or other commercial and public-domain editors may be used. 6 ROS Sysop Manual 4.3. ROS configuration file - CONFIG.ROS Table 4-4 lists the parameters which tailor ROS for your system. These parameters should be consolidated into the file CONFIG.ROS which will be interpreted during the initial startup. The file consists of entries with two components: the parameter and the value. In addition, comments, starting with a semi-colon (";"), may be freely included in the file. If a parameter is not in- cluded in the file, or if the file is not found, ROS will use the listed default value. Remember, it is not necessary to include all of these entries in CONFIG.ROS, only those that are different from the listed default values. In fact, the fewer entries there area, the faster ROS will start. Parameter Default Notes SysName ROS Name to be listed in the system directory. HDPark 0 Number of hard disk drives to park (seek to an unused track) when waiting for a caller. "0" inhibits the park function. "1" or "2" are other allowable values. TimeoutShort 60 Short time-out in seconds. This is the period allowed callers to complete their login and the length of time to wait for a keystroke during the login process. Since many users will set their modem on auto-dial and leave, it does not need to be very long. TimeoutLong 300 Long time-out in seconds. This is the period ROS will wait for a keystroke once the user has completed the login process. DefAcc 10 New user access level. This is the access level assigned to first-time callers. RegAcc 11 Registered user access level. This is the access level assigned to the user when the registration information is completed. ROS does not check for content during the regi- stration process, only that the user at least tried. 7 ROS Sysop Manual ValAcc 20 Validated user access level. This is the access level assigned when the <V>alidate user command is selected from the sysop sub-system. DirAcc 20 System directory access level. File areas with this access level or lower will be included in the system directory. Normally this will be the same as "ValAcc" (above) but there may be special situations which require this flexibility. AltSysop 250 Alternate sysop access level. Users with this access level or higher can perform any operation on the system except <C>opy and <D>elete files in the sysop sub- system. PriSysop 255 Primary sysop access level. Users with this access level or higher (255 is the limit) can do anything on the system. LPDAcc 250 The time limit is per day for users below this access level. At or above this level, the limit is per call. DefTime 15 Default time limit. This is the time allotted first time callers. ValTime 45 Time limit for validated users. When users are validated, their access level will be increased to this value. DefChars 80 Default characters per line. This value will be inserted in the user record as the number of characters per line. The user can change this value in the Utility sub-system. DefLines 23 Default lines per page. Similar to "DefChars." DefMsgArea POST Default message area. Until changed by the user, this will be the message area they first see when calling the system. DefFilArea LOGIN Default file area. Similar to "DefMsgArea." 8 ROS Sysop Manual ChatStart 19 Chat period start time. From this hour (24 hour clock) until "ChatEnd" ROS will signal the sysop by ringing the console bell when the user requests chat from the Utility sub-system. During other hours, ROS will just offer to save a message. ChatEnd 22 Chat period ending time. ChatSignals 10 Number of times to signal local console. Each attempt takes approximately 6 seconds. Fence | Character between directory columns. It can be any printable character, including a blank (" "). UnvDays 7 Days to retain unvalidated user. When the sysop function to urge users is selected, ROS will delete all unvalidated users that have not called the system in "UnvDays." ValDays 180 Days to retain validated users. Similar to "UnvDays" but for validated users. For more information, refer to the sysop urge command. ReadDays 10 Days to retain read, undeleted mail (private messages). Mail that has been read but not deleted will be purged this number of days after entry. UnrdDays 90 Days to retain unread, undeleted messages. Any message, public or private, will be purged this number of days after entry. NewinDays 14 Days since upload (or creation) to retain files in the NEWIN file area DustyDays 30 Days since last download to retain files in the DUSTY file area OtherDays 180 Days since last download to retain files in other areas MaxTries 3 Maximum number of tries for password. If the user cannot enter their password in "MaxTries" attempts, ROS will offer to leave a message and then disconnect. 9 ROS Sysop Manual OpenSystem Y The default, an open system, will allow new users to enter a password and receive limited access. When logging out, ROS will ask them to register for more access. A closed system will refuse access to new users. The sysop MUST preload the user with the associated password before the system will recognize him. TrimHiBit Y Text may either be stripped to seven bit characters or left alone. If a text editor, such as WordStar in document mode, is used for SYSMTXT.ROS, "Y" should be used to prevent sending non- ASCII characters. If eight-bit graphics characters are desired, "N" should be selected. ComPort 1 Port to be used for all modem I/O (either "1" or "2" may be used). ComParity N Parity to set port. The following characters may be used: "N" => None "E" => Even "O" => Odd ComLength 8 Number of bits in characters to be received and transmitted. ComStop 1 Number of stop bits in each character. CmndReset AT Z{ Modem reset string - sent at startup and connect failures. RespReset OK Expected response string from modem to indicate successful reset. WaitReset 5 Seconds to wait before assuming failure. CmndInit AT E1 H0 Q0 S0=0 S7=30 V1 X4 M0{ Modem initialization string - sent before EACH call to ensure the modem is ready for the next call. RespInit OK Response if successful. WaitInit 5 Seconds to wait for success. CmndBusy AT H1{ Make line busy. RespBusy OK Response if successful. WaitBusy 5 Seconds to wait for success. 10 ROS Sysop Manual CmndLocal ~~~+++ Return modem to local mode (escape code). RespLocal OK Response if successful. WaitLocal 5 Seconds to wait for success. CmndHangup AT H{ Disconnect - hang-up. RespHangup OK Response if successful. WaitHangup 5 Seconds to wait for success. RespRing RING Ring signal detected. CmndAnswer AT A{ Answer call - pick up phone. RespAnswer Response if successful. WaitAnswer 5 Seconds to wait for success. RespConnect CONNECT 1200 Connect message. ROS supports up to seven of the following baud rates: 110, 150, 300, 1200, 2400, 4800, 9600, and 19,200. The first "RespConnect" entry will be used for off-line communication with your modem and should usually be the fastest speed the modem can handle. RateConnect 1200 Rate to set the communications port when this message is received from the modem. RespConnect CONNECT Connect message. RateConnect 300 Rate to set for this message. . Additional connect messages and . rates . WaitConnect 15 Seconds to wait for connect message. RespError ERROR Error in command execution. This is the message sent by the modem when an error is detected. BGMain 0 Main window background color (see table 4-5 for the color scale) FGMain 7 Main window character color BGStat 7 Status window background color FGStat 0 Status window character color BGSend 0 Send window background color FGSend 7 Send window character color BGRecv 0 Receive window background color FGRecv 7 Receive window character color Table 4-4: Configuration Parameters 11 ROS Sysop Manual In the modem command strings described in table 4-4, a left brace ("{") is used to send a carriage return to the modem. A tilde ("~") causes a delay for 1/2 second before continuing. For example, "~~~+++" delays for 1 1/2 seconds, and then sends "+++" to the modem. Command strings may be up to 50 characters long (though most modems only allow 40 characters not including the prefix "AT," spaces, or the carriage return), responses may be as long as 16 characters. The modem initialization string listed in table 4-4 for "CmndInit" works well with "real" Hayes modems. Figure 4-1 gives a description of each element in the string. |get modem's attention | |modem should echo characters when off-line | | |ensure phone hung up | | | |return result codes ("Resp---") | | | | |disable auto answer | | | | | |wait 30 seconds for carrier | | | | | | |verbose (words) result codes | | | | | | | |enable extended command set | | | | | | | | |turn off the speaker | | | | | | | | | |command terminator AT E1 H0 Q0 S0=0 S7=30 V1 X4 M0{ Fig. 4-1: Hayes Modem Initialization Command String Some modems respond with "OFF HOOK" when issued the command "ATA". Those that do may need the following definition: RespAnswer OFF HOOK Response if successful 0 Black 8 Dark Gray 1 Blue 9 Light Blue 2 Green 10 Light Green 3 Cyan 11 Light Cyan 4 Red 12 Light Red 5 Magenta 13 Light Magenta 6 Brown 14 Yellow 7 Light Gray 15 White Table 4-5: Color Scale 12 ROS Sysop Manual 4.4. System message file - SYSMTXT.ROS SYSMTXT.ROS, the system message file, should be created for your particular system. A sample file is included as a guideline. When ROS is started, it looks for NDXSYSM.ROS. If found, it will be used as an index into the text file. If it is not found, ROS will create it from SYSMTXT.ROS. When you change SYSMTXT.ROS, ROS will detect the changes and automatically rebuild NDXSYSM.ROS. Since many messages are used during operation, SYSMTXT.ROS is divided into sections. Each section starts with a colon (":") in column one, followed by a unique two or three character identifier. If three characters are used, the third character will always be an "A" indicating the following message is to be sent to users operating in ANSI mode. For example, your SYSMTXT file might contain two menus for the message sub-system. The first, for users with only ASCII capability would be keyed with ":HM". The second, for users that can display ANSI control codes, would be named ":HMA". Table 4-6 describes the entries in this file. :WM Welcome text This text is displayed to the user before the system asks for the user's name. :GM Goodbye text This is the text displayed just before the system disconnects. :B0 Bulletin automatically displayed at login This is the text displayed after the user logs into the system and when "B" is selected while in the message system. :B1-:B9 User selected bulletins These are the texts displayed when the user presses "1" - "9." :OS Other systems This is the text displayed when the user selects "O" while in the message system. 13 ROS Sysop Manual :NF Name search failed If ROS cannot find the user name, this text will be displayed. Open systems: old users should be asked to try again, new users will be told that they can register on-line. Closed systems: this text will be the last thing an unauthorized user will see. You may leave this completely blank or tell the user what he has to do to register. :PF Password match failed If the user enters an incorrect password, this text will be displayed. :IN Information for new users This text will be displayed the first time a user calls and whenever "I" is selected while in the message system. :RR Registration request This text will be displayed if the unregistered user selects "R" while in the utility system or if he answers yes to the registration question. :AR Transfer from within an archive When a user starts to transfer a file from within an archive, this text will be displayed. :UD Upload description Before starting an upload, this text will be displayed. :ME Displayed to the user when the F8 key is pressed on the local console. :HM * Help for message sub-system This is the message sub-system help menu. :HF * Help for file sub-system This is the file sub-system help menu. 14 ROS Sysop Manual :HU * Help for utility sub-system This is the utility sub-system help menu. :HC * Help for system configuration This menu will be displayed when the user selects "A" while in the utility system. :HS * Help for sysop Sub-system This is the sysop system help menu. :HE * Help for editing text This text will be displayed when the user edits a message or when the sysop edits a macro. :HT Help for transfer mode selection This text will be displayed when the user changes the file transfer mode. :HP * Help for purge file command This text will be displayed to the sysop when purging files. :HL * Help for list file command This text will be displayed to the sysop when listing system files. :HR * Help for edit user record This text will be displayed when editing user records. :HA * Help for alter message status This text will be displayed when changing the status of messages. :HN * Help for catalog file status changes This text will be displayed to the sysop when changing the status (hidden, released, etc.) of files in the catalog. 15 ROS Sysop Manual :HI * Help for information displayed during user listing This text will be displayed to the sysop when listing users. :HY * Help for catalog system This text will be displayed to the sysop when using the catalog system. :HZ * Help for catalog record editor This text will be displayed to the sysop when making changes to the catalog entries. * automatic display if the current help level is 3. Otherwise available by pressing "?" when in the associated context. Table 4-6: System Message Text File 4.5. Other files used by ROS When the area, configuration, and system message files are ready, ROS can be started. If it cannot find the other files it ex- pects, it will create them. Table 4-7 lists the files ROS uses. AREA.ROS See section 4.2 for a complete description CONFIG.ROS See section 4.3 for a complete description SYSMTXT.ROS See section 4.4 for a complete description NDXSYSM.ROS Index file into SYMSTXT.ROS. LOG.ROS Log of activities on the system. MACRO.ROS This is a text file that may be edited outside of ROS or with the macro functions in the sysop sub-system. Since most communication packages now include scripts, macros, or the equivalent, ROS only supports this feature for the sysop. MESSAGE.ROS This file contains the text of messages and mail. SUMMARY.ROS This file contains the header and subject information for the messages and mail. 16 ROS Sysop Manual CATDAT.ROS This file contains the descriptions and other statistical information for all files on the system. Portions of this file are displayed with the <D>irectory command in the file sub- system. It is edited with the <C>atalog command in the sysop sub-system. NDXCATN.ROS These files provide fast access to the catalog NDXCATD.ROS file (CATDAT.ROS). STATS.ROS This file contains the counters used by ROS to keep track of users, callers, time usage, etc. USERDAT.ROS These are the user records. To conserve disk space, "SUMMARY.ROS", "CATDAT.ROS", and "LOG.ROS" maintain pointers into this file instead of storing the entire user name. NDXUSER.ROS This is the index file into USERDAT.ROS. Table 4-7: Files Used by ROS 17 ROS Sysop Manual 5. USING THE SYSTEM ROS expects to find all files in the file area (sub-directory) in which it first starts. It is here that the user files, log file, etc. will be maintained. Since ROS provides the sysop with full control over who has access to this area through access level, two methods protect the ROS system files from users: 1. do not include this area in the AREA.ROS file, or 2. set the access level of this area sufficiently high, such as 250 or higher. In a similar manner, other private areas of the disk system can be protected from users. In the example AREA.ROS file, "ROSRUN" can only be accessed by the sysop. Other users will not even know the area exists. 5.1. Logging in the first time When you run ROS the first time, it will create the files it needs. ROS will signon and let you know what files it is making and then get the modem ready. When the message "ROS ready..." appears on the status line, ROS is in an idling state and is ready for one of two actions: 1. a signal from the modem indicating an incoming call, or 2. a command from the console indicating a local user. To log in locally, press the carriage return (refer to section 5.4.1 for additional information). After the "FIRST name>" prompt appears, enter "SYSOP" as your first name. This is a special name ROS recognizes and will inhibit display of the "LAST name>" prompt. Since this is the first time you have been on the system, ROS will prompt for a password - enter one of your choice. You are now logged into the system. As the sysop, you are automatically assigned an access level as defined in CONFIG.ROS by "PriSysop" and an access time defined by "ValTime." CAUTION: It is very important that you log in using the name "sysop" before making the system available for others to use. Since there are folks out there that will try to log in as sysop, if you have not set your password, they will set it for you and will consequently have full sysop level access! 5.2. Status line When a user is logged into ROS, a status line of the following form will be displayed: Rate | Time on-Time left | Access level | Name | City, State 18 ROS Sysop Manual 5.3. When ROS is idling between users When ROS is idling, i.e. waiting for a call, the CRT screen will be cleared and a time of day clock will be displayed to indicate that ROS is operational. This clock will invert its colors every two seconds to ensure there is no chance of screen burn. 5.4. Local console commands The local console has several commands, entered by function keys, that may be used while the system is idling and while a user is logged in remotely. In either condition, pressing function key "F1" will display a list of the commands that ROS will accept. If ROS is idling, pressing this key will display the following on the status line: F7: Internal, F10: Shutdown, C/R: Local use If the command line parameter "/d" was included when ROS was started, the following will be displayed instead: F2: Direct, F7: Internal, F10: Shutdown, C/R: Local use If a user is logged on remotely, pressing "F1" will display the following on the status line: F3: Delay, F4: Remote, F5: Chat, F6: Signal, F8: Message, F9: Twit Since no function key commands are available when logged in at the local console, pressing "F1" while in this mode will have no effect. Each of these commands is described in the following sections. 5.4.1. C/R Using ROS locally When ROS is idling, pressing the C/R ("Enter") key will take the modem off hook and allow you to proceed as if you were a remote caller. All operations except file transfer are available. In this mode, ROS will assume a connect rate as specified by the first "RateConnect" entry in the CONFIG.ROS file when displaying file transfer times in a file directory. 5.4.2. F2 Direct connection When started with the "/d" command line parameter, ROS will bypass normal modem commands to allow high-speed direct connection to another computer. This command initiates the connection at the rate specified by the first "RateConnect" entry in the CONFIG.ROS file. 19 ROS Sysop Manual 5.4.3. F3 Delayed disable This command toggles the system disable function so that when the current user logs out, the modem will be made busy and the the bell will be sounded to indicate that ROS avail- able for local use. The function is helpful in getting control of a busy system. While the user is still logged in, this command may be used to alternately turn the func- tion on and off. 5.4.4. F4 Disable remote I/O This command alternately disables and re-enables the output to the remote system. Disabling the remote I/O is useful since local operations can proceed at full speed without waiting for the relatively slow modem. With the remote I/O disabled, the access level of the system is temporarily set to "AltSysop" level. When remote I/O is restored, the ac- cess level is reinstated to its original value. The in- creased access level is convenient to validate users while they are still logged in, move files that the user could not otherwise get to, etc. 5.4.5. F5 Sysop initiated CHAT ROS will issue a message to the remote user and then enter the chat mode. This command bypasses the time-of-day checks and may be entered at any time (chat hours are restricted to users). 5.4.6. F6 Signal key This command turns off the chat signal without any indica- tion to the user. 5.4.7. F7 Internal key This command causes immediate execution of the time initiated macro. See section 6.8.1 for more information. 5.4.8. F8 Message key This command sends the message identified by the key ":ME" in the SYSMTXT.ROS file. Use this to ask a user to log off the system if, for example, bad weather is approaching. 20 ROS Sysop Manual 5.4.9. F9 Twit key This command will cause ROS to immediately hang up on the remote user. While the F3 command is preferred to gain system access, this command is sometimes necessary. 5.4.10. Shutdown ROS F10 When ROS is idling, entering this command will terminate ROS operation and return control to the operating system. ROS will first ask if the modem should be taken off the hook to present a busy signal to users. This is useful when the system will be down for a short time. 21 ROS Sysop Manual 6. MAINTENANCE The sysop(s) should regularly use ROS to read mail, validate new users, and release (or not) the new files uploaded to the system. A check may also be made of other messages and mail to ensure that they are appropriate to the philosophy of the system. Be- ware of messages and mail which contain credit card numbers, computer access codes, or other sensitive information. Since the message file only marks messages as deleted, it should be compressed periodically. A good way to do this is to turn on the printer or the audit trail, list the log and message files, then turn the printer off and purge the files. This way, a hard- copy record is kept of all activity on the system. Not re-using the message space was a conscious design decision to allow the sysop to maintain a history of ALL messages entered on the system. The events surrounding the MOGUR BBS demonstrate the need. 6.1. Sysop Sub-system The sysop command system is accessed by typing "X" at a message, file, or utility command sub-system prompt. This command is not available to users below the alternate sysop access level ("AltSysop" is defined in CONFIG.ROS). Figure 6-1 lists the sysop sub-system commands. This menu may be displayed at any time by entering "?" (without the quotes). Subsequent sections describe each command in detail. Sysop Sub-System =============== Functions =============== == System Changes == <A>udit trail toggle <L>ist system files <G>oodbye (logoff) <C>atalog operations <O> Macro operations <F>ile Sub-System <E>dit user record urge files <M>essage Sub-System nitialize files <T>oggle printer tility Sub-System <J>ump to DOS <V>ersions <X>pert toggle Fig. 6-1: Sysop Sub-System 6.2. <A>udit trail toggle This command allows you to create a standard ASCII text file from any system output. The audit trail file name consists of the system date and a numeric extension - starting with zero. For example, the first time the audit trail is enabled on the 15th of 22 ROS Sysop Manual December 1986, the name would be 86-12-15.000. If the audit trail were turned off and then back on later in the same day, the file name would be 86-12-15.001. 6.3. <C>atalog operations This command provides access to the file catalog and posting system. Each operation is described in the following sections. Refer to appendix C for more information on setting up a new catalog. 6.3.1. uild This command builds two files, "CATALOG" and "CATALOG.BRF" which are the contents of the catalog. The full catalog includes the descriptions of the files. The second, brief catalog only lists the file areas, file names, and file sizes from the catalog. The sysop will be prompted as to which catalog to build with each execution of this command. 6.3.2. <D>escribe Many sources are currently available for the descriptions that are to be included in your catalog. These sources include other bulletin board systems, catalog files you may be currently main- taining by hand, and other catalog systems. ROS provides this command to make use of these sources to speed the development of your catalog. When this command is executed, ROS will prompt for a file name (a full path name including drive may be entered) that contains file names and descriptions in the following format: name.ext description "name.ext" is the file name and extension of a file which may be in your catalog and "description" is the description of that file. 50 characters of description are allowed. After accepting the file name (a null name will exit this func- tion), ROS will prompt for the column in which the description starts. ROS will then ask whether or not it should update existing descriptions. If the default "No" response is entered, only blank descriptions will be updated. If ROS finds the file name in the current cata- log, and its description is currently blank, the description from the specified text file will be added. Existing descriptions will not be overwritten nor will files which are not in the cata- log be added. This command will only update descriptions of catalog entries which are currently blank. In addition, once a description has been used, it will not be used again. So, if you 23 ROS Sysop Manual have two files with the same name in your catalog, only one have a description added. But, since this command will not change existing descriptions, it may be used several times. Each time, one of these duplicate entries will pick up the description. IF YOU ANSWER "Yes", EXISTING DESCRIPTIONS WILL BE CHANGED. This option is useful if you want to edit your existing CATALOG with your favorite word processor and then feed this catalog back into ROS. NOTE: duplicate file names in different file areas may produce unexpected results since only the first entry will be changed. Use this option with care. This command may even be used to restore a completely destroyed catalog if the text file "CATALOG" is still available. Simply specify "CATALOG" for the input text file and column 29 for the column in which the description starts. For example, call another local BBS or two and download their descriptions. These descriptions do not have to be in any spe- cial order, nor does ROS care if there are blank lines or lines with special characters. What it is looking for is an exact match of the file name in columns 1-12 of the file. If this is found and the current catalog description is blank, the text description will be added to the catalog. 6.3.3. <E>dit This command allows the sysop to display and edit catalog en- tries. If the command has not been previously executed in the current session, the first record in the default file area will be displayed. Subsequent entries into this command will redis- play record displayed the last time the command was used. The following sections describe the commands that may be entered. 6.3.3.1. Add This command may be used to add a new record to the catalog. 6.3.3.2. Backward This command changes the displayed record to the last record in the previous file area (as defined in the AREA.ROS file). File areas "wrap" around so that if already displaying a record in the first file area, the last file area will be displayed. 6.3.3.3. Change ROS will prompt for and move to a new file area. The first entry in the specified area will be displayed. 24 ROS Sysop Manual 6.3.3.4. Delete This command will delete the current catalog entry and its assoc- iated file. Both actions are verified before taking place. 6.3.3.5. Edit This command allows the sysop to edit several fields in the cata- log record. These fields are as follow: Home area This is the file area in which the file will spend most of its time. When a file is added to the system, by an upload or directly, this field should be set to reflect the file area most appropriate to the content of the file. For example, a new file, MYCB.ARC is uploaded to the system. The "current area" (below) will be set to NEWIN automatically. Upon determining the file is another checkbook balancing program, the sysop may determine that the file belongs in the ACCOUNTING file area. The "home area" should be set to "ACCOUNTING." After the file has been in the NEWIN area for a time, it will be moved to the ACCOUNTING area when the ost command is executed. Current area This is the file area where the file can presently be found. IF THIS FIELD IS CHANGED, THE FILE WILL BE AUTOMATICALLY RELOCATED TO ITS NEW DOS SUB-DIRECTORY. This is done to maintain the accuracy of the catalog in relation to the system directory. Name The name of the file Description The textual description of the file Size The file size in bytes Accesses The number of times the file has been accessed. If the file is a library (.LBR) or archive (.ARC), this field will be incremented each time the file is opened. For text files, this field will be incremented each time the file is typed. Finally, this field will be incremented each time the file is downloaded using Xmodem Normal editing commands are available. Please refer to the User Manual for more information on the editor. 6.3.3.6. Forward Similar to "Backward," ROS will display the first record in the next file area. Again, file areas wrap around. 25 ROS Sysop Manual 6.3.3.7. Hide This command will hide the current catalog entry from normal users, i.e. without sysop access level, the record will not be displayed when the file sub-system directory command is executed, nor will the file be included in the text file "CATALOG." This attribute is automatically set when ROS adds a file that has the DOS hidden attribute and when new files are uploaded to the sys- tem. When this command is executed, the DOS hidden attribute is also set for the physical file. 6.3.3.8. Next The next alphabetical catalog entry will be displayed. If there are no more entries in the current file area, the next file area will be entered and displayed, with wrap around as for the For- ward command. 6.3.3.9. Previous The previous alphabetical catalog entry will be displayed. If there are no more entries in the current file area, the previous file area will be entered and displayed, with wrap around as for the Backward command. 6.3.3.10. Release This command is used to release for user view, a hidden file. The DOS hidden attribute is also reset. 6.3.3.11. Select This command allows the sysop to select a new file name for dis- play. In a fashion similar to the "Whereis" command, ROS does not require a complete file name and will move to the first matching file name in the current file area. 6.3.3.12. Quit This command exits the catalog entry editor. 6.3.4. <G>lobal This command changes the "home" and "current" area fields from one value to another. For example, you have decided that "TOOLS" is a better file area name than "PROGRAMS." After editing the AREA.ROS file, you start ROS and enter this command to effect the change for all the catalog entries. No files are moved, only the catalog and its associated index files are updated. NOTE: If the AREA.ROS is changed and the catalog entries are not, the users 26 ROS Sysop Manual will not have access to the files. 6.3.5. <L>eaders This command lists the 15 most frequently accessed files. 6.3.6. ost This command automatically performs most of the housekeeping that a large file repository, such as a BBS, needs. For example, new versions of files area added to the system, old versions must be purged, changes to the file area structure may have to be made, etc. With this command, the sysop is only required to enter the "home" area once for each new file. The name of file and its description are entered by the user and the other fields are set by the system when the file is uploaded. The "Upload date" and the "Last access" field are used to deter- mine when a posting action should take place. After a file has been in the NEWIN area for "NewinDays" days (defined in CONFIG.ROS), it will be moved to its Home Area. After a file has been in its Home Area for "OtherDays" days without being accessed, it will be moved to the DUSTY area. This area indi- cates to users that after "DustyDays" days without access, the file will be removed from the system. From DUSTY, the file is actually moved to the ARCHIVE file area which is not available to users. Files in this area then may be copied to a backup media such as floppy disk or tape and then deleted. The migration of files through the system can be displayed thus: NEWIN --> home area --> DUSTY --> ARCHIVE --> deleted ROS will not actually delete any files from the system. This is left to the sysop. Note the difference in the way ROS determines expiration for the NEWIN area compared to all other file areas: in NEWIN, "Upload date" is used, while "Last access" is used elsewhere. 6.3.7. <R>econcile This command is used to ensure the physical directory and the catalog maintained by ROS are in agreement. If changes in the file size, date, or status (hidden, released) are made, this command will detect these changes and update the catalog to re- flect them. If files are listed in the catalog, but not found in the disk directory, ROS will mark them as "Missing." If files are found in the disk directory, but not in the catalog, ROS will add them to the catalog. 27 ROS Sysop Manual 6.3.8. <Q>uit This command terminates the catalog edit session. 6.4. <E>dit user record When this command is entered the first time, ROS will display the first available entry in the user file. Subsequent entries of this command will display the record of the last user edited. The selected user record is displayed while ROS waits for a second command. The following sections define these secondary commands. 6.4.1. <A>dd record This command may be used to add a new user to the system. ROS will verify that the name does not already exist. If not, it will prompt for the new password and then display the record for further edits. This command is especially useful for closed systems where new users are not allowed to register on-line. 6.4.2. <D>elete record ROS will prompt to verify that this is the action desired. If so, it will delete the user and any messages addressed to or from that user. 6.4.3. <E>dit record The cursor will be positioned at the name field for editing using commands identical to those used for messages (refer to the User Manual). All fields except the time of last access are editable. ROS does not require precise entry of the user name to find a record for editing. It will find the record which is equal to OR GREATER THAN the entered name. For example, if you cannot remem- ber how John Smith spells his last name, enter "John" for the first name and "Smith" for the last name. ROS will find a record even if John spells his last name "Smithe." NOTE: Similar names can result in the display of a record other than the one desired. The sysop should verify that the desired user record is the one displayed. 6.4.4. <F>orce password ROS encrypts passwords in such a way that it cannot be decrypted - even the sysop cannot see the passwords. This encryption is done to provide a very high level of security, especially if the user file comes into the wrong hands. 28 ROS Sysop Manual This option allows the sysop to input a new password for the currently displayed user. The new password will echo as it is typed. 6.4.5. <N>ext record When this command is entered, ROS will find the next (alphabeti- cally) user record and display it for edit. Only records with access levels equal or less than the user will be displayed, e.g. alternate sysops cannot modify or even view the primary sysop record. 6.4.6. revious record When this command is entered, ROS will find the previous (alpha- betically) user record and display it for edit. Access level restrictions similar to those described for the next record apply. 6.4.7. <R>egistered This command will search the user file for the next (alphabetic- ally) user that has requested validation. When the user record is displayed on the screen, all editing commands are again avail- able. When ROS returns to the last user edited or selected, no more records have been found. 6.4.8. <S>elect record When this command is entered, ROS will prompt for a new user name and then display that user for edit. Access level restrictions similar to those described for the <N>ext record command apply. 6.4.9. <V>alidate user This command changes the access level and time allowance for the user being edited to the values defined in CONFIG.ROS ("ValAcc" and "ValTime"). It is more convenient than editing the user and can be performed easily from a remote site. 6.4.10. <Q>uit edit session When all user records have been edited, enter this command and ROS will return to the sysop sub-system. 6.5. nitialize system files This command is useful for sysops that normally operate their system from a remote site. With it, ROS can be forced to read new AREA.ROS and SYSMTXT.ROS files, normally only read at startup. When this command is executed, ROS will look for these 29 ROS Sysop Manual two files in the NEWIN file area. If either is found, it will replace the original file, ROS will read the new file(s), and begin to use the new values. For example, a remote sysop needs to change a message in SYSMTXT.ROS. The new file is uploaded and the nitialize command is used to allow ROS to start using this new file. 6.6. <J>ump to DOS This command allows rapid access to DOS through a shell. ROS is still loaded, but suspended, while DOS is made available to the sysop. All normal DOS commands are available either locally or remotely. The DOS command "EXIT" is used to return to ROS. 6.7. <L>ist system files When this command is entered, four secondary commands may be entered to select which file should be listed. The following sections define these secondary commands. 6.7.1. <A>ll system files This command will list both the log and the message files. 6.7.2. <L>og file ROS maintains a time and date tagged list of most system opera- tions. This command will display this list. From the informa- tion contained in this file, the sysop can determine what kind of activity the system is being used for, what users seem to be having problems, what users are abusing their privileges, etc. 6.7.3. <M>essages All messages after the specified date will be displayed in chron- ological order. 6.7.4. <Q>uit This command will return control to the sysop sub-system. 6.8. <O> Macro operations In addition to being able to read characters from either the keyboard or the remote channel, ROS can read from internal char- acter strings called "macros." These strings can be used to execute any sequence of operations as defined by the sysop. Since some of the system maintenance commands can take some time to complete, macros can be very convenient. 30 ROS Sysop Manual In addition to the text editing commands described in the User's Guide, pressing "B" for egin will cause ROS to prompt for the macro number to execute. Since the macro file is a standard text file, most text editors and word processors can also be used to edit the MACRO.ROS file. High bits in the file, as set by Word- Star in document mode, will confuse ROS. WordStar non-document mode is fine. ROS is still monitoring both the local and remote keyboards while processing a macro so the sysop can pause (^S) or cancel (^C) a command, but macro processing will continue until complete. Since a carriage return is used to terminate the entry of a new macro string, a slash (/) may be entered into the macro. When encountered, ROS will convert this character into a carriage return. As shown in the example, control characters may be entered by prefixing a standard letter with a carat ("^"). For example, CTRL-C may be inserted into a macro with the two charac- ter string "^C". 6.8.1. Time Initiated Macro If the macro starts with a colon and a time of day, e.g. ":00:15", ROS will use this time to automatically start the macro execution. Only one time initiated macro is allowed. 6.8.2. Macro Examples The sample macro file included with ROS performs the following: Macro #1 - :03:00 Sysop/password/xcrpbybnqob3/ :03:00 time to start the macro Sysop/ user name terminated with a carriage return password/ password terminated with a carriage return x enter the sysop sub-system c start the catalog processor r reconcile the catalog p post the files b build a new text catalog y include descriptions (CATALOG) b build another new text catalog n don't include descriptions (CATALOG.BRF) q quit the catalog processor o macro operations b begin macro number... 3/ ...three 31 ROS Sysop Manual Macro #2 - payn p purge a all files y yes, really do it n no, don't renumber messages Macro #3 - jARCHIVE/ j jump to DOS ARCHIVE/ use ARCHIVE.BAT for commands while in DOS g goodbye y yes, really log out The macro linkage shown at the end of macro number one is not necessary, but serves to show how linking macros is accomplished. 6.9. urge files This command purges and compresses selected files of deleted entries. It processes four different files, each selectable by a single command, or all four files together. All commands are verified before continuing. Sufficient disk space must be available for these operations or ROS will report an error and terminate. Should this happen, ROS will automatically recover from the old files the next time it is started, but extraneous files may be left on the disk. 6.9.1. Purge All This command purges all four files, i.e. it automatically performs a purge of the log, catalog, user, and message files. 6.9.2. Purge Catalog This command purges the file catalog system of any entries that are currently marked as "Missing." 6.9.3. Purge Log This command removes all entries from the log file. 6.9.4. Purge Messages As described in the introduction, deleting a message only marks that message for delete. To physically remove the message from the disk, the message files must be purged. 32 ROS Sysop Manual 6.9.5. Purge Users This command deletes all users that have not logged in within the times specified, in CONFIG.ROS, by either "UnvDays" (for unvali- dated users) or "ValDays" (for validated users). When a user is purged with this command, ROS will also mark any messages sent to or from that user for deletion. 6.10. <T>oggle printer The currently assigned LST device is alternately enabled and disabled. To prevent inadvertent toggling when no printer is connected, this command is verified before continuing. In addi- tion, ROS traps the DOS critical error handler and will issue warning 03-09 if the printer is not available. Processing will then continue. 6.11. <V>ersions This command displays the version numbers of DOS, DESQview (if installed), and ROS. 6.12. Other commands available to the sysop Naturally, all the user commands are available to the sysop in- cluding the ability to return to one of the other three command sub-systems. These commands are discussed below, as well as some enhancements to the commands that normal users have. 6.12.1. <G>oodbye (logoff) This command terminates the session. 6.12.2. <F>ile Transfer System This command causes ROS to exit the sysop sub-system and enter the file transfer sub-system. 6.12.3. <M>essage System This command causes ROS to exit the sysop sub-system and enter the message sub-system. 6.12.4. tility System This command causes ROS to exit the sysop sub-system and enter the utility sub-system. 6.12.5. <X>pert mode toggle In the sysop sub-system, pressing "X" will alternate between help 33 ROS Sysop Manual levels 1 and 3. In other sub-systems, pressing "X" will cause ROS to check the access level of the user. Sysops will enter the sysop sub-system and normal users will toggle their help level. 6.12.6. Command Enhancements 6.12.6.1. Changing a Message Status or Message Area After reading a message, the sysop will be given the option of altering the message area or status of the message. The options are as follow: <D>elete mark message as deleted ndividual mark message as private <M>ove move message to another message area (ROS will prompt for the new area name as defined in AREA.ROS) ublic mark message as public <R>ead mark message as having been read Note that all of these commands are available for any message that can be displayed, even one which is currently marked as "deleted." This allows the sysop to "un-delete" a message. 6.12.6.2. Setting the System Time and Date After displaying the time and date with the <T>ime command in the utility sub-system, ROS will allow the sysop to set these values. 6.12.6.3. User List Additions When the user list is requested, ROS will allow the sysop to enter one of four parameters: <A>ll List all fields in the user records. This listing may be captured by enabling the audit trail with the <A>udit command in the sysop sub-system. Table 6-1 lists the fields and their widths. This fixed field length format is ideal for input into a database management system such as dBase. <E>xceptional List users with an unusual access level or time limit. nvalidated List unvalidated, unregistered users. <Q>uick List user names only (this is the same listing normal users get). 34 ROS Sysop Manual Field name Field width First name 15 Last name 15 Address 30 City 20 State 2 Zip code 9 Phone 13 System 10 Access level 3 Time limit 3 Default message area 12 Default file area 12 Default transfer protocol 1 Nulls 2 Caps lock 1 ("T"rue or "F"alse) Prompt bell 1 ("T"rue of "F"alse) Help level 1 Columns 2 Lines 2 Times on 5 Date last on 18 Normal time 5 Total time 5 Last high message 10 Uploads 5 Downloads 5 Table 6-1: Format of User File Listing 35 ROS Sysop Manual 7. SECURITY The security of a computer system is of paramount importance when that system is readily available through the telephone system. To make ROS robust enough to withstand both incorrect entries and malicious attacks, a simple but effective method is used: an access level, ranging from 0 to 255, is assigned to each user. System privileges are based upon this number. In general, the higher the number, the greater the privileges the user has. The following access levels are recommended (set in CONFIG.ROS): 0-9 Twit - will be logged off immediately 10-19 Unvalidated user - limited message and files access 11 Registered user - has not yet been validated 20-249 Normal user - full message and files access 250-254 Alternate sysops 255 Primary sysop This access level structure allows sysops to review all user records in the system, including their own, but no one may change or even display the record of a user with a higher access level. CAUTION: The primary sysop can edit any user record, including his own. Care must be taken to not acciden- tally lower the sysop access level. ROS encrypts passwords to further ensure security. This encryption uses a "one-way" algorithm that has no simple inverse, i.e. the encrypted password cannot be readily converted into the un-encrypted password. While this should help protect against programs that attack the user file, the best security is to beware of "Trojan Horse" programs and to be very cautious with programs that you run on your system. 36 ROS Sysop Manual 8. COMMAND LINE OPTIONS Four command line options are recognized by ROS: /r reorganize user and catalog files /d direct connect - ignore modem responses /m modem information display /o= overlay file path These options may be used in any order, with or without spaces separating them. 8.1. Option /r ROS can recover from many types of damage to the user and catalog files, and it can recover from corrupted or even missing index files (in fact, if you suspect that your index files may have become corrupted, simply delete them. ROS will rebuild them as necessary. This includes NDXUSER.ROS, NDXCATN.ROS, NDXCATD.ROS, and NDXSYSM.ROS). To reorganize the user and catalog data files and subsequently rebuild the index files, you may add a "/r" to the command line. Normally, this option is not needed, but there may be times when it can improve or even restore system operation. For example, while ROS re-uses deleted records and keeps USERDAT.ROS and CATDAT.ROS as compact as possible, you may wish to use this option to remove the deleted records from the file. Another situation when this option is useful is after a long period of activity during which many users or catalog entries have been added to the system and many others have been deleted. ROS will always access these files in alphabetical order, but it may do so with quite a bit of disk activity due to the nature of the file. With this option, ROS will sort these files to minimize the disk thrashing needed for sequential access. The third situation in which you may need to recover your data and index files should never occur, but a disk failure or other serious system problem could cause damage to the data or index files. If you suspect that any of these files may be damaged, use this option. ROS commits to disk all system files frequently to minimize data loss. You can even reset or power down the computer while ROS is running without serious consequences, though this is not recommended. During execution, ROS will display counts of records processed and the supported data files on which it is working. 37 ROS Sysop Manual 8.2. Option /d This option causes ROS to ignore the modem. It is useful in two situations. First, there may be situations when you do not have a modem connected to the serial port or the modem is already off- hook and you do not want to hang up. Since modem commands and modem responses are inhibited with this command, it may also be used when there is no modem connected at all. In fact, the system may be connected to another computer. Pressing "F2" will initiate a session with that local computer. 8.3. Option /m To assist in setting up your modem, the command line parameter "/m" may be used to open a one line window at the bottom of the screen. In this window, ROS will display all ASCII characters that are sent to and received from the modem. The left half of this line displays the characters sent to the modem, the right half displays what the modem has sent back. A left pointing triangle is used to indicate a carriage return, and a down poin- ting arrow indicates a line feed. 8.4. Option /o= ROS will normally look in the default sub-directory of the default drive for its overlays. There are occasions however when it is useful to start ROS from another area. For example, running two systems on one computer under DESQview. The first system is started in the default drive/directory. The second system is run on another drive or another sub-directory, but it uses the same program and overlay files as the first. For example, the command would be: c:\abq-ros\ros /o=c:\abq-ros The first part ("c:\abq-ros\ros") tells DOS where to go to find the ROS.COM file. The second part ("/o=c:\abq-ros") tells ROS where to find its overlay files. This option is also valuable if you have a RAMdisk. By putting the overlay files in RAMdisk, ROS can get the overlays it needs very quickly, speeding up the system and reducing drive wear. Putting ROS.COM in the RAMdisk is of little value since once it is loaded into memory further accesses are not required. 38 ROS Sysop Manual 9. OTHER VERSIONS OF ROS Index File Naming Conventions All index files used by ROS begin with "NDX". At any time, the NDX*.ROS files may deleted without damage to your system, though it will take longer to start the next time. When you perform your regular system backups (you do, don't you?), none of these index files need to be stored since they can be rebuilt from the other data files. The following cross-references the old name to the new: USERIDX.ROS -> NDXUSER.ROS SYSMIDX.ROS -> NDXSYSM.ROS CATDNDX.ROS -> NDXCATD.ROS CATNNDX.ROS -> NDXCATN.ROS These changes should be made before starting your new version of ROS. ROS file update utility - ROS37-38.COM ROS37-38.COM converts version 3.7 data files into the format expected by version 3.8. The original files will still exist but with a file extension of "BAK" (backup). Once you are satisfied that the new files operate correctly, the backup files may be deleted. NOTE: ROS37-38.COM will only operate correctly on standard ver- sion 3.7 format files. Attempts to run the program using files from other versions of ROS, including version 3.8 or modified versions of ROS may result in output files full of junk. 39 ROS Sysop Manual A. CONNECTING THE MODEM The single most common problem sysops have had with setting up a new ROS installation has been with the modem: "my computer works fine with Procomm, but hangs when I run ROS." Since the rest of the system hardware (disks, memory, etc.) is compatible at the DOS level, ROS can count on what will be available. But, since DOS does not support interrupt driven communication port input- output (I/O), ROS has to bypass DOS and even the BIOS, to get to the modem. In addition, "compatible" modems almost never are. Even models made by the same manufacturer may respond differently to com- mands. Sometimes these differences are marked, such as "NO DIAL TONE" instead of "DIAL TONE." More often, the differences are subtle, such as whether or not the modem returns a CR/LF before and after verbal responses. One modem does on some responses and not on others. Another modem even changes baud rate WHILE IT IS SENDING the connect response to the computer! ROS is designed to be robust in the way it handles the modem and "hooks" are provi- ded to be able to get to almost everything the modem and ROS need. Nonetheless, experimentation may be required to get a new modem operational. Start with the simplest command string that works and add to it if necessary. Usually, the initialization string will require the most work. Most terminal emulation programs such as Procomm or Qmodem use open-loop control, i.e. they assume that the modem understood the command it was sent, although they do monitor the modem for some command responses, such as "BUSY" or "CONNECT." ROS on the other hand, is expected to operate for long periods of time without attention, and thus drives the modem in closed-loop mode, i.e. all characters sent to the modem are expected to be echoed by the modem back to the computer. Then, ROS waits for the modem to respond to the command with a result code. For example, when ROS commands the modem to go off-hook (answer an incoming call), the modem should eventually tell ROS at what baud rate the connection was made or that the connection failed. When attaching a modem to ROS, then, be sure that the modem swit- ches are set to allow "modem echo" and "result code display." In addition, set the modem to use "verbal (word) messages" since this matches the CONFIG.ROS file that is included with ROS. You may, of course, modify the configuration file and then set the modem to return "numeric result codes." The only exception to the need for a character by character echo is during the modem reset string ("CmndReset" in CONFIG.ROS). 40 ROS Sysop Manual Some modems do not have a switch for "modem echo" and must be set into this mode through a command. "CmndReset" should be used for this. If the modem requires a time delay after it is reset until it will accept another command, use tilde characters ("~") as required. Brace characters ("{") may also be included in this string to complete each command and start another. For example, to reset a modem, wait for two seconds, and set the echo mode, the following "CmndReset" string could be used: ATZ{~~~~ATE1{ Two other common switch settings should be considered. The RS- 232C Data Carrier Detect (DCD) is used by ROS to determine whe- ther or not a connection is still valid. In other words, ROS monitors DCD and will terminate a session if it determines that DCD has been lost. Most modems have a switch setting that allows the modem to control DCD, based on the condition of the connec- tion, or to force DCD always on. The modem should be set to control DCD. Another switch determines in what way the modem will respond to Data Terminal Ready (DTR). This signal, coming from the computer and controlled by ROS, may be used to enable or disable the modem. For example, when a user completes a session and ROS tries to hang-up the modem, it first drops DTR. If the modem is set to disconnect when DTR is dropped, ROS will immediately see the loss of DCD and will recycle between callers very quickly. If after a few seconds, DCD is still present, ROS will send the local mode escape sequence ("CmndLocal" in CONFIG.ROS) and then the hang-up sequence ("CmndHangup" in CONFIG.ROS) to disconnect the caller. These steps take a little longer than simply drop- ping DTR. Some modems control DTR response through commands. These com- mands may be included in the reset or initialization strings sent to the modem ("CmndReset" or "CmndInit") instead of, or in addi- tion to, the switch settings. Finally, some modems can be set to automatically answer the phone when a ring is detected. This function should be disabled since ROS will tell the modem when to answer the phone. When you are satisfied that ROS and the modem are communicating properly, just start ROS without the "/M" to improve the local display appearance. 41 ROS Sysop Manual B. BUILDING A NEW FILE CATALOG Using commands built into ROS and existing description files can greatly simplify the process of building a new file catalog. After starting the session, enter the sysop sub-system. Enter "C" to start the catalog processor and then enter "R" to recon- cile the catalog with the disk directories. Since the catalog is currently empty, ROS will add the files it finds to the catalog. After ROS completes this process, enter a "D" to describe what has been added. This command will read an existing text file that may describe many of the files you have. After this process is complete, you may enter a "B" to build the textual catalog ("CATALOG") for users to download. If there are many gaps in "CATALOG," you might consider editing this file using a word processor and using this edited file as input to the describe command. Existing descriptions will not be altered, but newly added descriptions will be put into the catalog system. 42 ROS Sysop Manual C. WARNING AND ERROR MESSAGES When ROS encounters an error or a situation it cannot handle, it will issue a message in one of the following forms: "Warning xx-yy" or "Error xx-yy" The warning message is recoverable and ROS will continue to operate if possible. Errors are fatal and will result in the termination of processing. The most common warning message will probably be "Warning 01-F1" indicating that ROS could not find the sub-directory indicated in the AREA.ROS file. Editing that file will usually correct the problem. Only two class 2 errors should ever be seen, "F0" and "FF." The first, "F0" may occur if you have specified an incor- rect path in the command line using the "/o=" option; if you have started ROS in a sub-directory that does not contain the overlay files; or if ROS does not have enough file handles. Make sure line "FILES=20" (or more) is included in your CONFIG.SYS file (see section 4.1 for more information). The second error could occur if you have insufficient memory or if you are running ROS in a window that is not large enough. Running under DesqView, ROS requires a 160k window. The most common type three error will be a warning that the printer is not on-line, "Warning 03- 09." The most common type four error will probably be "Error 04- 18" which indicates that ROS cannot access LCOMX. LCOMX must be run before ROS. Other messages may be seen which indicate problems that should be corrected before continuing. 43 ROS Sysop Manual Class 0 - Miscellaneous: 01 ^C entered 02 Undefined error 03 Undefined I/O error 04 Could not open primary data or index file Class 1 - I/O: 01 File does not exist 02 File not open for input 03 File not open for output 04 File not open 10 Error in numeric format 20 Operation not allowed on a logical device 21 Not allowed in direct mode 22 Assign to standard files not allowed 90 Record length mismatch 91 Seek beyond end-of-file 99 Unexpected end-of-file F0 Disk write error F1 Directory full or missing F2 File size overflow F3 Too many open files FF File disappeared Class 2 - Run-time: 01 Floating point overflow 02 Floating point divide by zero 03 Negative square root argument 04 Integer divide by zero or negative ln argument 10 String length exceeds 255 11 String index out of range 90 Array index out of range 91 Scalar or subrange assignment out of range 92 Integer assignment out of range F0 Overlay file not found FF Heap/stack collision Class 3 - DOS critical errors: 00 Attempt to write on write-protected disk 01 Unknown unit 02 Drive not ready 03 Unknown command 04 Data error (CRC) 05 Bad request structure length 06 Seek error 07 Unknown media type 44 ROS Sysop Manual 08 Sector not found 09 Printer out of paper 0A Write fault 0B Read fault 0C General failure Class 4 - Async I/O: 00 Operation Successful 02 Invalid COM port number - must be 1 or 2 03 COM port is not open 04 Invalid parameters level 0 06 No serial port found 07 Output Queue Full 09 COM port already open 0A Input Queue is empty 14 Improper parameter specified 15 Input Queue Size too small 16 Output Queue Size too small 17 Interrupt level out of range 18 LCOMX has not been loaded 1F Invalid baud rate 20 Invalid parity specification 21 Invalid number of data bits requested 22 Invalid number of stop bits requested 23 Both Bit Trimming and Forcing attempted 24 Bit Forcing/Trimming requires 8 data bits 25 Invalid Break time 64 Internal Level Two Error FF Internal Level Zero Error Class 5 - Catalog maintenance: 00 Move successful 01 Source area not found 02 Destination area not found 03 Source file not found 04 Destination file already exists 05 Could not create destination file 06 Could not delete source file 07 Could not update catalog Table C-1: Error Messages 45 ROS Sysop Manual D. ROS USAGE AND PROBLEM REPORT Your comments and suggestions are important as they help improve and develop ROS. Please feel free to file this report more than once. Thanks in advance for taking the time to complete and send this questionnaire. Your name: Date: / / Company: Address: Please give a brief description of how you use ROS: When did you first receive ROS? What version are you now running? What type of computer is it used on? What is your average usage per day? Do you have any experience with similar products, even on other computers? If so, please describe: How long have you been using computers? Using a scale of 1-10 (1=very bad, 10=very good), please indicate your feelings about the following: The system performance: The system operations manual: The user manual: 46 ROS Sysop Manual The ease of use: The practicality or usefulness of this product: Your overall satisfaction: The overall satisfaction of your users: What would you say are the BEST features of ROS? What would you say are the WORST features of ROS? List any extraneous or useless features: List any enhancements you would like to see added: Describe any problems you have encountered, including examples if possible: 47 ROS Sysop Manual E. INVOICE Steven Fox Date: / / 2112 White Cloud NE Albuquerque, NM 87112 Name, address, phone: Product Quantity Price Each Total ROS License Fee ________ @ $35.00 _______ Total: _______ Please make checks payable to Steven Fox. Retain a copy of this invoice for your records. 48 Index INDEX <A>dd record, 28 <A>ll system files, 30 <A>udit trail toggle, 22 uild, 23 <C>atalog operations, 23 <D>elete record, 28 <D>escribe, 23 <E>dit, 24 <E>dit record, 28 <E>dit user record, 28 <F>ile Transfer System, 33 <F>orce password, 28 <G>lobal, 26 <G>oodbye (logoff), 33 nitialize system files, 29 <J>ump to DOS, 30 <L>eaders, 27 <L>ist system files, 30 <L>og file, 30 <M>essage System, 33 <M>essages, 30 <N>ext record, 29 <O> Macro operations, 30 ost, 27 revious record, 29 urge files, 32 <Q>uit, 28, 30 <Q>uit edit session, 29 <R>econcile, 27 <R>egistered, 29 <S>elect record, 29 <T>oggle printer, 33 tility System, 33 <V>alidate user, 29 <V>ersions, 33 <X>pert mode toggle, 33 Add, 24 Backward, 24 BUILDING A NEW FILE CATALOG, 42 C/R Using ROS locally, 19 Change, 24 Changing a Message Status or Message Area, 34 Command Enhancements, 34 COMMAND LINE OPTIONS, 37 Configuring DOS, 4 CONNECTING THE MODEM, 40 49 Index Delete, 25 Edit, 25 F2 Direct connection, 19 F3 Delayed disable, 20 F4 Disable remote I/O, 20 F5 Sysop initiated CHAT, 20 F6 Signal key, 20 F7 Internal key, 20 F8 Message key, 20 F9 Twit key, 21 FILES, 3 Forward, 25 Hide, 26 HISTORY AND ACKNOWLEDGMENTS, 1 INSTALLING ROS, 4 INVOICE, 48 Local console commands, 19 Logging in the first time, 18 Macro Examples, 31 MAINTENANCE, 22 Message and file area control file - AREA.ROS, 4 MINIMUM SYSTEM, 2 Next, 26 Option /d, 38 Option /m, 38 Option /o=, 38 Option /r, 37 Other commands available to the sysop, 33 Other files used by ROS, 16 OTHER VERSIONS OF ROS, 39 Previous, 26 Purge All, 32 Purge Catalog, 32 Purge Log, 32 Purge Messages, 32 Purge Users, 33 50 Index Quit, 26 Release, 26 ROS configuration file - CONFIG.ROS, 7 ROS USAGE AND PROBLEM REPORT, 46 SECURITY, 36 Select, 26 Setting the System Time and Date, 34 Shutdown ROS, 21 Status line, 18 Sysop Sub-system, 22 System message file - SYSMTXT.ROS, 13 Time Initiated Macro, 31 User List Additions, 34 USING THE SYSTEM, 18 WARNING AND ERROR MESSAGES, 43 When ROS is idling between users, 19 51